System for triggering cross channel data caching on network nodes

ABSTRACT

Embodiments of the present invention provide a system for triggering cross channel data caching on network nodes. Historical event data and live event data of a user may be monitored to determine an expected event that includes one or more expected channels. An expected period of time for the expected event may also be determined. Relevant user data may then be identified from one or more systems of record and cached or otherwise compressed. One or more nodes of a network associated with each of the one or more expected channels are then identified. The cached data is then transmitted to virtual data structures associated with each of the one or more nodes. The cached data is then generally maintained in these virtual data structures on the network for the expected period of time.

BACKGROUND

Supporting remote databases or servers having limited hardware capacity(including limited central processing units, limited random accessmemory, and limited bandwidth) with time-sensitive data from a centrallocation has involved the transmittal of cached data in response todetermining that these remote databases or servers require the data.Typical cache replacement policies of least recently used (LRU), firstin first out (FIFO), time aware least recently used (TLRU), and the likehave been used to maintain the cached data at each of these remotedatabases and servers.

BRIEF SUMMARY

The following presents a summary of certain embodiments of theinvention. This summary is not intended to identify key or criticalelements of all embodiments nor delineate the scope of any or allembodiments. Its sole purpose is to present certain concepts andelements of one or more embodiments in a summary form as a prelude tothe more detailed description that follows.

Embodiments of the present invention address the above needs and/orachieve other advantages by providing apparatuses (e.g., a system,computer program product and/or other devices) and methods fortriggering cross channel data caching on network nodes. The systemembodiments may include one or more memory devices havingcomputer-readable program code stored thereon, a communication device,and one or more processing devices operatively coupled to the one ormore memory devices, where the one or more processing devices areconfigured to execute the computer-readable program code to carry outthe invention. In computer program product embodiments of the invention,the computer program product includes at least one non-transitorycomputer-readable medium including computer-readable instructions forcarrying out the invention. Computer implemented method embodiments ofthe invention may include providing a computing system including acomputer processing device and a non-transitory computer-readablemedium, where the computer-readable medium includes configured computerprogram instruction code, such that when the instruction code isoperated by the computer processing device, the computer processingdevice performs certain operations to carry out the invention.

For sample, illustrative purposes, system environments will besummarized. The system may monitor historical event data of a customerand live event data of the customer and determine an expected eventbased on the historical event data of the customer and the live eventdata of the customer. In some embodiments, the expected event mayinclude one or more expected channels. The system may identify, from oneor more systems of record, a set of data associated with the customer,based on the expected event and cache the set of data associated withthe customer to generate a set of cached data. The system may identifyone or more nodes of a network associated with each of the one or moreexpected channels, where each of the one or more nodes is associatedwith one or more adapters configured to format the set of cached datainto formats compatible with each of the one or more expected channels.The system may generate on each of the one or more nodes a virtual datastructure and transmit the set of cached data to the virtual datastructure on each of the one or more nodes, where the set of cached datais converted into the formats compatible with each of the one or moreexpected channels by the one or more adapters.

In some embodiments, determining the expected event may includedetermining an expected event period of time based on a configuration ofthe network, and the system may maintain the set of cached data in eachvirtual data structure on each of the one or more nodes for the expectedevent period of time.

In some embodiments, determining the expected event may includedetermining an expected event period of time, and the system maymaintain the set of cached data in each virtual data structure on eachof the one or more nodes for the expected event period of time.Additionally, or alternatively, the system may determine that theexpected event period of time has concluded, determine that the expectedevent is not occurring, and, in response to determining that theexpected event period of time has concluded, and in response todetermining that the expected event is not occurring, delete the set ofcached data from each virtual data structure on each of the one or morenodes. In some embodiments, the system may determine that the expectedevent is occurring, determine that the expected event period of time hasconcluded, and maintain the set of cached data in each virtual datastructure on each of the one or more nodes for at least as long as theexpected event is occurring.

In some embodiments, determining the expected event may includedetermining an expected event period of time for each of the one or moreexpected channels.

In some embodiments, the expected event may include an expectation thatthe customer will access an online portal while in a foreign geographicregion, where a first channel of the one or more expected channelsincludes the online portal linked to a first node of the network locatedin the foreign geographic region, and where transmitting the set ofcached data to each virtual data structure on each of the one or morenodes includes transmitting the set of cached data to the first node.

In some embodiments, the expected event may include an expectation thatthe customer will contact a managing entity by calling the managingentity or by physically visiting an office of the managing entity, wherea first channel of the one or more expected channels includes aninteractive voice response application linked to a first node of thenetwork, where a second channel of the one or more expected channelsincludes an office records system associated with the office of themanaging entity that is linked to a second node of the network, andwhere transmitting the set of cached data to each database associatedwith each of the one or more expected channels includes transmitting theset of cached data to a first virtual data structure on the first nodeand to a second virtual data structure on the second node.

In some embodiments, each node of the network may be connected toanother node of the network, and connected nodes of the network mayinclude virtual data structures including corresponding sets of cacheddata.

In another aspect, the present invention may include a computer programproduct for triggering cross channel data caching on network nodes, andthe computer program product may include at least one non-transitorycomputer-readable medium including computer-readable instructions. Insome embodiments, the instructions may include instructions formonitoring historical event data of a customer and live event data ofthe customer and determining an expected event based on the historicalevent data of the customer and the live event data of the customer,where the expected event includes one or more expected channels. Theinstructions may include instructions for identifying, from one or moresystems of record, a set of data associated with the customer, based onthe expected event, and caching the set of data associated with thecustomer to generate a set of cached data. The instructions may includeinstructions for identifying one or more nodes of a network associatedwith each of the one or more expected channels, where each of the one ormore nodes is associated with one or more adapters configured to formatthe set of cached data into formats compatible with each of the one ormore expected channels. The instructions may include instructions forgenerating on each of the one or more nodes a virtual data structure andtransmitting the set of cached data to the virtual data structure oneach of the one or more nodes, where the set of cached data is convertedinto the formats compatible with each of the one or more expectedchannels by the one or more adapters.

In some embodiments, determining the expected event may includedetermining an expected event period of time based on a configuration ofthe network, and the computer-readable instructions may includeinstructions for maintaining the set of cached data in each virtual datastructure on each of the one or more nodes for the expected event periodof time.

In some embodiments, determining the expected event may includedetermining an expected event period of time, and the computer-readableinstructions may include instructions for maintaining the set of cacheddata in each virtual data structure on each of the one or more nodes forthe expected event period of time. Additionally, or alternatively, thecomputer-readable instructions may include instructions for determiningthat the expected event period of time has concluded, determining thatthe expected event is not occurring, and in response to determining thatthe expected event period of time has concluded, and in response todetermining that the expected event is not occurring, deleting the setof cached data from each virtual data structure on each of the one ormore nodes. In some embodiments, the computer-readable instructions mayinclude instructions for determining that the expected event isoccurring, determining that the expected event period of time hasconcluded, and maintaining the set of cached data in each virtual datastructure on each of the one or more nodes for at least as long as theexpected event is occurring.

In some embodiments, determining the expected event may includedetermining an expected event period of time for each of the one or moreexpected channels.

In some embodiments, the expected event may include an expectation thatthe customer will access an online portal while in a foreign geographicregion, where a first channel of the one or more expected channelsincludes the online portal linked to a first node of the network locatedin the foreign geographic region, and where transmitting the set ofcached data to each virtual data structure on each of the one or morenodes includes transmitting the set of cached data to the first node.

In some embodiments, the expected event includes an expectation that thecustomer will contact a managing entity by calling the managing entityor by physically visiting an office of the managing entity, where afirst channel of the one or more expected channels includes aninteractive voice response application linked to a first node of thenetwork, where a second channel of the one or more expected channelsincludes an office records system associated with the office of themanaging entity that is linked to a second node of the network, andwhere transmitting the set of cached data to each database associatedwith each of the one or more expected channels includes transmitting theset of cached data to a first virtual data structure on the first nodeand to a second virtual data structure on the second node.

In some embodiments, each node of the network may be connected toanother node of the network, and connected nodes of the network mayinclude virtual data structures including corresponding sets of cacheddata.

In yet another aspect, the present invention may include a computerimplemented method for triggering cross channel data caching on networknodes, where the computer implemented method includes providing acomputing system including a computer processing device and anon-transitory computer-readable medium, where the computer-readablemedium includes configured computer program instruction code, such thatwhen the instruction code is operated by the computer processing device,the computer processing device performs operations. In some embodiments,the operations may include monitoring historical event data of acustomer and live event data of the customer and determining an expectedevent based on the historical event data of the customer and the liveevent data of the customer, where the expected event includes one ormore expected channels. Additionally, or alternatively, the operationsmay include identifying, from one or more systems of record, a set ofdata associated with the customer, based on the expected event andcaching the set of data associated with the customer to generate a setof cached data. In some embodiments, the operations may includeidentifying one or more nodes of a network associated with each of theone or more expected channels, where each of the one or more nodes isassociated with one or more adapters configured to format the set ofcached data into formats compatible with each of the one or moreexpected channels. Additionally, or alternatively, the operations mayinclude generating on each of the one or more nodes a virtual datastructure and transmitting the set of cached data to the virtual datastructure on each of the one or more nodes, where the set of cached datais converted into the formats compatible with each of the one or moreexpected channels by the one or more adapters.

In some embodiments, determining the expected event includes determiningan expected event period of time based on a configuration of thenetwork, and the computer program instruction code includes computerprogram instruction code, such that when the instruction code isoperated by the computer processing device, the computer processingdevice maintains the set of cached data in each virtual data structureon each of the one or more nodes for the expected event period of time.

The features, functions, and advantages that have been discussed may beachieved independently in various embodiments of the present inventionor may be combined with yet other embodiments, further details of whichcan be seen with reference to the following description and drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described embodiments of the invention in general terms,reference will now be made the accompanying drawings, wherein:

FIG. 1 provides a block diagram illustrating a system environment fortriggering cross channel data caching on network nodes, in accordancewith an embodiment of the invention;

FIG. 2 provides a block diagram illustrating the managing entity systemof FIG. 1 , in accordance with an embodiment of the invention;

FIG. 3 provides a block diagram illustrating the expected eventidentification system of FIG. 1 , in accordance with an embodiment ofthe invention;

FIG. 4 provides a block diagram illustrating the cached datatransmission triggering system of FIG. 1 , in accordance with anembodiment of the invention;

FIG. 5 provides a block diagram illustrating the computing device systemof FIG. 1 , in accordance with an embodiment of the invention; and

FIG. 6 provides a flowchart illustrating a process for triggering crosschannel data caching on network nodes, in accordance with embodiments ofthe invention.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

Embodiments of the present invention will now be described more fullyhereinafter with reference to the accompanying drawings, in which some,but not all, embodiments of the invention are shown. Indeed, theinvention may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein; rather, theseembodiments are provided so that this disclosure will satisfy applicablelegal requirements. Where possible, any terms expressed in the singularform herein are meant to also include the plural form and vice versa,unless explicitly stated otherwise. Also, as used herein, the term “a”and/or “an” shall mean “one or more,” even though the phrase “one ormore” is also used herein. Furthermore, when it is said herein thatsomething is “based on” something else, it may be based on one or moreother things as well. In other words, unless expressly indicatedotherwise, as used herein “based on” means “based at least in part on”or “based at least partially on.” Like numbers refer to like elementsthroughout.

Embodiments of the present invention provide a system and method fortriggering cross channel data caching on network nodes. In general, thesystem will determine that a particular event is likely to happen atsome point in the near future, and define this event as an “expectedevent.” The expected event generally is a future action between acustomer and a managing entity (e.g., a financial institution), wherethis future action is predicted to occur during a determined oridentified period of time (e.g., after at least ten minutes, but withinthe next four hours), and where the future action may occur through oneor more “channels.” The channels are the communication channels,portals, customer support systems, automated teller machines, electronickiosks, physical offices, and the like that facilitate communicationbetween the customer and the managing entity (e.g., a managing entitycomputing system, an employee of the managing entity, or the like).

Once the expected event has been identified and/or defined, the systemwill then identify customer data that may be needed during the expectedevent from one or more systems of record. Once the customer data hasbeen pulled, the customer data is cached to reduce the size of the datafor data transmission purposes. Next, the system can identify one ormore nodes of a network associated with each of the one or more expectedchannels. Each of the one or more nodes may be associated with one ormore adapters for each channel, where the adapters are configured tore-format the cached data into one or more formats that are compatiblewith the adapter's respective channel(s). The system may generate, oneach of the one or more nodes, a virtual data structure, and thentransmit the cached data to the virtual data structure on each of thenodes. When one of the channels needs the cached data, the cached datais re-formatted by the adapters and transmitted, from the node(s) to thechannel. The cached data can be maintained in these nodes and/or virtualdata structures for the identified expected period of time so that thechannels will have the customer's data readily available prior to thecustomer initiating the interaction with the managing entity through theassociated channel. By storing the cached data in nodes and/or virtualdata structures of the network, the cached data may be stored near eachchannel to reduce network latency. For example, the cached data may livein transit on the network and act as cached data to consuming channels.In some embodiments, the network may be an ultra-fast network (e.g., 5Gand/or the like), and the data rate may be high enough that the cacheddata may live in transit on the network.

FIG. 1 provides a block diagram illustrating a system environment 100for triggering cross channel data caching, in accordance with anembodiment of the invention. As illustrated in FIG. 1 , the environment100 includes a managing entity system 200, an expected eventidentification system 300, a cached data transmission triggering system400, one or more computing device system(s) 500, a customer historicalevent database 120, a customer live event database 130, one or moresystems of record 140, one or more cached data adapters 160, one or morechannels 170, and one or more third party systems 180. One or more users110 may be included in the system environment 100. In some embodiments,the user(s) 110 of the system environment 100 may be a customer of amanaging entity that owns or otherwise controls the managing entitysystem 200.

The managing entity system 200, the expected event identification system300, the cached data transmission triggering system 400, the computingdevice system(s) 500, the customer historical event database 120, thecustomer live event database 130, the systems of record 140, the cacheddata adapter(s) 160, the one or more channels 170 (including one or moreremote databases or servers linked with or otherwise associated witheach of the one or more channels), and/or the third party system 180 maybe in network communication across the system environment 100 throughthe network 150. The network 150 may include a local area network (LAN),a wide area network (WAN), and/or a global area network (GAN). Thenetwork 150 may provide for wireline, wireless, or a combination ofwireline and wireless communication between devices in the network. Inone embodiment, the network 150 includes the Internet. In someembodiments, the network includes a wireless telephone network 152.

The managing entity system 200 may be a system owned or otherwisecontrolled by a managing entity to perform one or more process stepsdescribed herein. In some embodiments, the managing entity is afinancial institution. In general, the managing entity system 200 isconfigured to communicate information or instructions with the expectedevent identification system 300, the cached data transmission triggeringsystem 400, the computing device system(s) 500, the customer historicalevent database 120, the customer live event database 130, the systems ofrecord 140, the cached data adapter(s) 160, the one or more channels170, and/or the third party system 180 across the network 150. Forexample, the managing entity system 200 may monitor the customerhistorical event database 120 and/or the customer live event database130. The managing entity system 200 may also be configured to identifycustomer data from the systems of record 140. The managing entity system200 may also be configured to communicate monitored or identified datato the expected event identification system 300, the cached datatransmission triggering system 400, the computing device system 500, thecached data adapter(s) 160, the channels 170, and/or a third partysystem 180. Of course, the managing entity system 200 may be configuredto perform (or instruct other systems to perform) one or more otherprocess steps described herein. The managing entity system 200 isdescribed in more detail with respect to FIG. 2 .

The expected event identification system 300 may by a system owned orcontrolled by the managing entity and/or a third party that specializesin monitoring historical and live event data of a customer, identifyingtriggering actions, determining an expected event (including expectedchannels associated with the expected event and an expected period oftime associated with the expected event). In general, the expected eventidentification system 300 is configured to communicate information orinstructions with the managing entity system 200, the cached datatransmission triggering system 400, the computing device system(s) 500,the customer historical event database 120, the customer live eventdatabase 130, and/or the third party system 180 across the network 150.In some embodiments, at least a portion of the expected eventidentification system 300 is a component of the managing entity system200. Furthermore, the expected event identification system 300 mayutilize artificial intelligence and/or machine learning engines orsystems to perform one or more of the functions described herein.

For example, the expected event identification system 300 may monitorthe customer historical event database 120 and the customer live eventdatabase 130 to detect a triggering action and determine an expectedaction for the customer based on the monitored data. The expected eventidentification system 300 can also communicate the expected action andany data or information related to the expected action to the managingentity system 200 and/or the cached data transmission triggering system400. Of course, the expected event identification system 300 may beconfigured to perform (or instruct other systems to perform) one or moreother process steps described herein. The expected event identificationsystem 300 is described in more detail with respect to FIG. 3 .

The cached data transmission triggering system 400 may by a system ownedor controlled by the managing entity and/or a third party thatspecializes in identifying customer data from one or more systems ofrecord (e.g., the systems of record 140), caching data, and transmittingcached data to certain channels (e.g., the channels 170), possiblythrough one or more cached data adapters (e.g., the cached data adapters160). In general, the cached data transmission triggering system 400 isconfigured to communicate information or instructions with the managingentity system 200, the expected event identification system 300, thecomputing device system(s) 500, the systems of record 140, the cacheddata adapter(s) 160, the one or more channels 170, and/or the thirdparty system 180 across the network 150. In some embodiments, at least aportion of the cached data transmission triggering system 400 is acomponent of the managing entity system 200. Furthermore, the cacheddata transmission triggering system 400 may utilize artificialintelligence and/or machine learning engines or systems to perform oneor more of the functions described herein. In some embodiments, thecached data transmission triggering system 400 may include a transmitterserver for transmitting cache data to one or more nodes of the network150. Additionally, or alternatively, one or more of the cached dataadapter(s) 160 may be associated with one or more nodes of the network150.

In some embodiments, the cached data transmission triggering system 400may be configured to receive an expected event (or informationassociated with an expected event) from the expected eventidentification system 300. The cached data transmission triggeringsystem 400 may also be configured to identify customer data from thesystems of record 140. In some embodiments, the cached data transmissiontriggering system 400 may be configured to run cached data through thecached data adapters 160. Additionally, or alternatively, the cacheddata transmission triggering system 400 may be configured to transmitcached data to one or more nodes of the network 150 associated with thechannels 170, and the cached data adapters 160 may be configured toformat the cached data from the one or more nodes of the network 150into formats compatible with an associated one or more of the channels170. Of course, the cached data transmission triggering system 400 maybe configured to perform (or instruct other systems to perform) one ormore other process steps described herein. The cached data transmissiontriggering system 400 is described in more detail with respect to FIG. 4.

The computing device system 500 may by a system owned or controlled bythe managing entity, the user 110, and/or a third party that specializesin providing computing devices to users (e.g., the user 110) and/orproviding data and receiving user inputs from computing devices inconjunction with the system embodiments herein. In general, thecomputing device system 500 is configured to communicate information orinstructions with the managing entity system 200, the expected eventidentification system 300, the cached data transmission triggeringsystem 400, the customer historical event database 120, the customerlive event database 130, the systems of record 140, the one or morecached data adapters 160, and/or the third party system 180 across thenetwork 150.

For example, the computing device system 500 may be operated orotherwise owned by a customer, where the computing device system 500provides real-time data (e.g., location data, customer action data,transaction data of the customer using a computing device, onlinetraffic data, and the like) to the customer live event database 130. Insome embodiments, a computing device system 500 may be associated withone or more channels 170, where the computing device system 500 mayreceive transmitted cached data of a customer from the cached datatransmission triggering system 400 and/or the cached data adapter(s)160. Of course, the computing device system 500 may be configured toperform (or instruct other systems to perform) one or more other processsteps described herein. The computing device system 500 is described inmore detail with respect to FIG. 5 .

The customer historical event database 120 may include a networkcommunication interface, a processing device, and one or more memorydevices, where the processing devices are configured to perform certainactions with the memory devices and communicate these actions to therest of the network 150 through the network communication interface. Thedata or information stored in the customer historical event database 120may include, but is not limited to, any data, information, data trends,and/or the like that can be used to identify or determine correlationsbetween certain triggering actions. For example, the data stored in thecustomer historical event database 120 may include information abouttriggering events that have prompted a customer (e.g., the user 110) tointeract with a managing entity associated with processes describedherein.

A triggering action may be the action of a notification being sent tothe customer (e.g., the user), where the notification indicates that apayment cannot be processed, that an issue with an account of the userhas been identified, and/or the like. The triggering action may also bean action performed by the user without a prompt by the managing entity(e.g., purchasing a travel ticket to another geographic region, changingownership or access rights to an account associated with the user,purchasing a particular product or service, and/or the like). Thehistorical event data may include information about which events appearto have been triggered by the triggering action.

For example, if the triggering action was a notification that atransaction cannot be processed, the triggered event (i.e., historicalevent) may have been for the customer to call a customer support line ofthe managing entity, call a representative of the customer that worksfor the managing entity, log into an online portal, physically visit anoffice of the managing entity, interact with an automated teller machineassociated with the managing entity, interact with an electronic kioskof the managing entity, and/or the like. This information can be storedin the customer historical event database 120.

The data stored in the customer historical event database 120 mayfurther include information about an amount of time between thetriggering action and the historical event (i.e., the time periodbetween when the triggering action and a starting time of the historicalevent).

For example, for a particular historical event, the system may determinethat the customer called into a customer support line of the managingten minutes after receiving a notification that a transaction of thecustomer could not be processed. Furthermore, the system can determinehow long each historical event took, and store this information ashistorical event data in the customer historical event database 120.

The system can also store information about trends, averages, and otherstatistical information in the customer historical event database 120.For example, the system can determine that it takes the customer anaverage of thirty minutes to call into a particular customer supportline after a particular triggering action, with a lower limit of tenminutes and an upper limit of two hours. The system can also determinean amount of time that the customer was engaged in each historicalevent, an average amount of time that the customer has been engaged inthe same type of historical events, lower and upper limits of the amountof time that the customer has been engaged in the same type ofhistorical events, and/or the like. As such, the system can storeinformation about expected periods of time that the customer may beengaging with that particular type of event. For example, the system canestablish an expected period of time of a particular type of event asbeginning at the lower limit of the amount of time to begin the event,and lasting for the amount of time associated with the upper limit ofhow long the customer has been engaged with the event. Of course, thesystem can also add or subtract a certain percentage (e.g. five percent,ten percent, and/or the like) or period of time (e.g., ten minutes, fivehours, and/or the like) to the expected period of time that the customercould be engaged with the particular type of event. In some embodiments,the system may also take into account or use the expected periods oftime of other customers.

The historical event data stored in the customer historical eventdatabase may also identify one or more channels (e.g., the channels 170)that the customer uses when interacting with the managing entity duringeach historical event. As there are several potential events that may belikely or predictable for each triggering action, the system mayidentify and store a likelihood that the customer will interact witheach channel in response to a particular triggering event or triggeringevent type (each interaction, or the set of possible interactionstogether, being referred to as an expected event) within the customerhistorical event database 120.

The customer live event database 130 may include a network communicationinterface, a processing device, and one or more memory devices, wherethe processing devices are configured to perform certain actions withthe memory devices and communicate these actions to the rest of thenetwork 150 through the network communication interface. The monitoredcustomer live event database 130 may include data, information, alerts,news stories, current transaction data, and/or the like that isassociated with the particular customer, associated with the particulartype of customer, and/or associated with information that may have animpact on whether a triggering event is occurring or is likely to occur.The customer live event database 130 data may include similarinformation to the customer historical event database, but the liveevent database may receive constant, real-time, and/or near real-timeupdates to its data to inform the system on currently-occurring actions,notifications, incidents, and other occurrences that may trigger thesubsequent occurrence of an expected event.

Each of the systems of record 140 may include a network communicationinterface, a processing device, and one or more memory devices, wherethe processing devices are configured to perform certain actions withthe memory devices and communicate these actions to the rest of thenetwork 150 through the network communication interface. The systems ofrecord 140 may include any information storage system(s) withauthoritative data, linkages, customer information, account information,and/or the like, as stored, owned, maintained, and/or otherwise managedby the managing entity. In some embodiments, multiple systems of record140 may be included in the system environment 100. For example, a firstsystem of record 140 may be associated with customer account data, asecond system of record 140 may be associated with transactionprocessing data for the managing entity, a third system of record 140may be associated with access entitlements associated with the managingentity, and/or the like.

The cached data adapter(s) 160 may include one or more devices,applications, systems, and/or the like that are configured to convertthe cached data into a format that is readable or otherwise accessibleto a particular channel of the channels 170. For example, a firstadapter may be configured to convert cached data into a format that iscompatible with databases that are local to a channel of a recordssystem for a physical office. Additionally, a second adapter may beconfigured to convert cached data into a format that is compatible witha database in a foreign geographical region that supports an onlineportal in that foreign geographical region. Furthermore, a third adaptermay be configured to convert cached data into a format that iscompatible with databases that are local to or otherwise linked with aninteractive voice response application channel. As such, the cached dataadapter(s) 160 may be configured to receive cached data in a first dataformat from the systems of record 140, the cached data transmissiontriggering system 400, and/or one or more nodes of the network 150.

The channels 170 represent modes of interacting with the managingentity. The channels 170 may include, but are not limited to, dialinginto a customer support line, dialing into a customer representativeline, dialing into an interactive voice response line, logging into orotherwise accessing an online portal, logging into or otherwiseaccessing a mobile application portal while in a particular geographicalregion, and/or the like. Each of the channels 170 may be associated withor linked with one or more nodes of the network 150 from which systemsof the channels 170 can extract the cached data to perform one or moreactions. For example, each of the channels 170 may be associated with orlinked with one or more nodes of the network 150 that are proximate tothe channel (e.g., physically proximate, proximate from a networkarchitecture perspective, proximate within the network 150, and/or thelike). In some embodiments, each of the channels 170 may be associatedwith or linked with one or more virtual data structures on one or morenodes of the network 150 from which systems of the channels 170 canextract the cached data to perform one or more actions. Additionally, oralternatively, when a channel extracts cached data from one or more ofthe virtual data structures and/or one or more nodes, one or more of thecached data adapters 160 may be configured to format the cached datainto formats compatible with the channel extracting the cached data.

The third party system 180 may be any other system that performs one ormore of the steps, procedures, actions, or the like described herein.

FIG. 2 provides a block diagram illustrating the managing entity system200 in greater detail, in accordance with embodiments of the invention.As illustrated in FIG. 2 , in one embodiment of the invention, themanaging entity system 200 includes one or more processing devices 220operatively coupled to a network communication interface 210 and amemory device 230. In certain embodiments, the managing entity system200 is operated by a first entity, such as a financial institution,while in other embodiments, the managing entity system 200 is operatedby an entity other than a financial institution.

It should be understood that the memory device 230 may include one ormore databases and/or other data structures/repositories. The memorydevice 230 also includes computer-executable program code that instructsthe processing device 220 to operate the network communication interface210 to perform certain communication functions of the managing entitysystem 200 described herein. For example, in one embodiment of themanaging entity system 200, the memory device 230 includes, but is notlimited to, a network server application 240, managing entityapplications 250 which include managing entity data 252, and othercomputer-executable instructions or other data. The computer-executableprogram code of the network server application 240, and/or the managingentity applications 250 may instruct the processing device 220 toperform certain logic, data-processing, and data-storing functions ofthe managing entity system 200 described herein, as well ascommunication functions of the managing entity system 200.

In one embodiment, a managing entity application(s) 250 includes a datamonitoring application, where customer historical event data, customerlive event data, and/or the like include the managing entity data 252.In such embodiments, the managing entity application 250 monitors datarelated to a customer (e.g., the user 110), and may be configured toidentify a triggering action from the customer data to identify anexpected event.

The managing entity application 250 may include a customer communicationapplication configured to transmit notifications, information, data,portals, software applications, and the like to one or more computingdevice systems 500 in the system environment 100.

The network server application 240 and the managing entityapplication(s) 250 may be configured to invoke and/or use the managingentity data 252 and/or the like when communicating through the networkcommunication interface 210 with the expected event identificationsystem 300, the cached data transmission triggering system 400,computing device systems 500, and/or the like.

FIG. 3 provides a block diagram illustrating the expected eventidentification system 300 in greater detail, in accordance withembodiments of the invention. As illustrated in FIG. 3 , in oneembodiment of the invention, the expected event identification system300 includes one or more processing devices 320 operatively coupled to anetwork communication interface 310 and a memory device 330. In certainembodiments, the expected event identification system 300 is operated bya first entity, such as a financial institution, while in otherembodiments, the expected event identification system 300 is operated byan entity other than a financial institution.

It should be understood that the memory device 330 may include one ormore databases and/or other data structures/repositories. The memorydevice 330 also includes computer-executable program code that instructsthe processing device 320 to operate the network communication interface310 to perform certain communication functions of the expected eventidentification system 300 described herein. For example, in oneembodiment of the expected event identification system 300, the memorydevice 330 includes, but is not limited to, a network server application340, one or more expected event identification applications 350 whichinclude event identification data 352, and/or other computer-executableinstructions or other data. The computer-executable program code of thenetwork server application 340, and/or the one or more expected eventidentification applications 350 may instruct the processing device 320to perform certain logic, data-processing, and/or data-storing functionsof the expected event identification system 300 described herein, aswell as communication functions of the expected event identificationsystem 300.

In some embodiments, an expected event identification application 350may include a data monitoring application configured to access, scan,analyze, trawl, pull, and/or otherwise monitor data and information fromthe customer historical event database 120 and/or the customer liveevent database 130. This data monitoring application may further beconfigured to identify, deduce, or otherwise determine and/or predict anexpected event from customer data identified from the customerhistorical event database 120 and/or the customer live event database130.

In some embodiments, an expected event identification application 350may include an artificial intelligence application and/or a machinelearning application that is configured to process data using aknowledge base and a built-in logic structure. As such, the artificialintelligence applications and/or machine learning applications may carryout at least a portion of the actions or steps performed by the expectedevent identification system 300, as described herein.

The network server application 340 and the one or more expected eventidentification applications 350 are configured to invoke and/or use theevent identification data 352 and/or the like when communicating throughthe network communication interface 310 with the customer historicalevent database 120, the customer live event database 130, the managingentity system 200, the cached data transmission triggering system 400,one or more computing device systems 500, and/or the like. Theprocessing device 320 is configured to use the network communicationinterface 310 to transmit and/or receive data and/or commands to and/orfrom the other devices connected to the network 150.

FIG. 4 provides a block diagram illustrating the cached datatransmission triggering system 400 in greater detail, in accordance withembodiments of the invention. As illustrated in FIG. 4 , in oneembodiment of the invention, the cached data transmission triggeringsystem 400 includes one or more processing devices 420 operativelycoupled to a network communication interface 410 and a memory device430. In certain embodiments, the cached data transmission triggeringsystem 400 is operated by a first entity, such as a financialinstitution, while in other embodiments, the cached data transmissiontriggering system 400 is operated by an entity other than a financialinstitution.

It should be understood that the memory device 430 may include one ormore databases and/or other data structures/repositories. The memorydevice 430 also includes computer-executable program code that instructsthe processing device 420 to operate the network communication interface410 to perform certain communication functions of the cached datatransmission triggering system 400 described herein. For example, in oneembodiment of the cached data transmission triggering system 400, thememory device 430 includes, but is not limited to, a network serverapplication 440, and one or more cached data transmission triggeringapplications 450 that include cached data transmission triggering data452, and other computer-executable instructions or other data. Thecomputer-executable program code of the network server application 440,and/or the one or more cached data transmission triggering applications450 may instruct the processing device 420 to perform certain logic,data-processing, and/or data-storing functions of the cached datatransmission triggering system 400 described herein, as well ascommunication functions of the cached data transmission triggeringsystem 400.

One embodiment of a cached data transmission triggering application 450includes a data caching application that is configured to receivecustomer data and cache the received customer data into a cache forcompressed storage. In such embodiments, the cached data may be stored,at least temporarily, within the cached data transmission triggeringsystem 400 as the cached data transmission triggering data 452.

Another embodiment of a cached data transmission triggering application450 includes a cached data transmission application that is configuredto transmit cached data to one or more nodes of the network 150associated with or linked to the one or more channels 170 of the systemenvironment 100. In some embodiments, the cached data transmissionapplication may be configured to first transmit the cached data to theone or more adapters 160 of the system environment 100 to have thecached data converted into a format that is compatible with remotedatabases associated with the one or more channels 170. Additionally, oralternatively, the cached data transmission application may beconfigured to transmit the cached data to the one or more nodes of thenetwork 150 and/or one or more virtual data structures on the one ormore nodes of the network 150 for storage on the network 150, and theone or more adapters 160 may convert the cached data into a format thatis compatible with the one or more channels 170 when the one or morechannels 170 extract the data from the one or more nodes and/or the oneor more virtual data structures on the network 150.

Furthermore, the cached data transmission triggering application 450 mayinclude or embody one or more artificial intelligence applicationsand/or systems or machine learning applications or systems that areconfigured to process data using a knowledge base and a built-in logicstructure. As such, the artificial intelligence applications and/ormachine learning applications may carry out at least a portion of theactions or steps performed by the cached data transmission triggeringsystem 400, as described herein.

The network server application 440 and the one or more cached datatransmission triggering applications 450 are configured to invoke or usethe cached data transmission triggering data 452 and/or the like whencommunicating through the network communication interface 410 with themanaging entity system 200, the expected event identification system300, the one or more computing device systems 500, the systems of record140, the cached data adapters 160, the channels 170, and/or the like.The processing device 420 is configured to use the network communicationinterface 410 to transmit and/or receive data and/or commands to and/orfrom the other devices connected to the network 150.

FIG. 5 provides a block diagram illustrating a computing device system500 of FIG. 1 in more detail, in accordance with embodiments of theinvention. In one embodiment of the invention, the computing devicesystem 500 is a mobile telephone. However, it should be understood thata mobile telephone is merely illustrative of one type of computingdevice system 500 that may benefit from, employ, or otherwise beinvolved with embodiments of the present invention and, therefore,should not be taken to limit the scope of embodiments of the presentinvention. Other types of computing devices may include portable digitalassistants (PDAs), pagers, mobile televisions, entertainment devices,desktop computers, workstations, laptop computers, cameras, videorecorders, audio/video player, radio, GPS devices, wearable devices,Internet-of-things devices, augmented reality devices, virtual realitydevices, automated teller machine devices, electronic kiosk devices,and/or any combination of the aforementioned.

Some embodiments of the computing device system 500 include a processor510 communicably coupled to such devices as a memory 520, user outputdevices 536, user input devices 540, a network interface 560, a powersource 515, a clock or other timer 550, a camera 580, and/or apositioning system device 575. The processor 510, and other processorsdescribed herein, generally include circuitry for implementingcommunication and/or logic functions of the computing device system 500.For example, the processor 510 may include a digital signal processordevice, a microprocessor device, and various analog to digitalconverters, digital to analog converters, and/or other support circuits.Control and signal processing functions of the computing device system500 are allocated between these devices according to their respectivecapabilities. The processor 510 thus may also include the functionalityto encode and interleave messages and data prior to modulation andtransmission. The processor 510 can additionally include an internaldata modem. Further, the processor 510 may include functionality tooperate one or more software programs, which may be stored in the memory520. For example, the processor 510 may be capable of operating aconnectivity program, such as a web browser application 522. The webbrowser application 522 may then allow the computing device system 500to transmit and receive web content, such as, for example,location-based content and/or other web page content, according to aWireless Application Protocol (WAP), Hypertext Transfer Protocol (HTTP),and/or the like.

The processor 510 is configured to use the network interface 560 tocommunicate with one or more other devices on the network 150. In thisregard, the network interface 560 includes an antenna 576 operativelycoupled to a transmitter 574 and a receiver 572 (together a“transceiver”). The processor 510 is configured to provide signals toand receive signals from the transmitter 574 and receiver 572,respectively. The signals may include signaling information inaccordance with the air interface standard of the applicable cellularsystem of the wireless telephone network 152. In this regard, thecomputing device system 500 may be configured to operate with one ormore air interface standards, communication protocols, modulation types,and access types. By way of illustration, the computing device system500 may be configured to operate in accordance with any of a number offirst, second, third, and/or fourth-generation communication protocolsand/or the like. For example, the computing device system 500 may beconfigured to operate in accordance with second-generation (2G) wirelesscommunication protocols IS-136 (time division multiple access (TDMA)),GSM (global system for mobile communication), and/or IS-95 (codedivision multiple access (CDMA)), or with third-generation (3G) wirelesscommunication protocols, such as Universal Mobile TelecommunicationsSystem (UMTS), CDMA2000, wideband CDMA (WCDMA) and/or timedivision-synchronous CDMA (TD-SCDMA), with fourth-generation (4G)wireless communication protocols, with LTE protocols, with 5GPPprotocols, with fifth-generation (5G) wireless communication protocols,and/or the like. The computing device system 500 may also be configuredto operate in accordance with non-cellular communication mechanisms,such as via a wireless local area network (WLAN) or othercommunication/data networks.

As described above, the computing device system 500 has a user interfacethat is, like other user interfaces described herein, made up of useroutput devices 536 and/or user input devices 540. The user outputdevices 536 include a display 534 (e.g., a liquid crystal display or thelike) and a speaker 532 or other audio device, which are operativelycoupled to the processor 510.

The user input devices 540, which allow the computing device system 500to receive data from a user such as the user 110, may include any of anumber of devices allowing the computing device system 500 to receivedata from the user 110, such as a keypad, keyboard, touch-screen,touchpad, microphone, mouse, joystick, other pointer device, button,soft key, and/or other input device(s). The user interface may alsoinclude a camera 580, such as a digital camera.

The computing device system 500 may also include a positioning systemdevice 575 that is configured to be used by a positioning system todetermine a location of the computing device system 500. For example,the positioning system device 575 may include a GPS transceiver. In someembodiments, the positioning system device 575 is at least partiallymade up of the antenna 576, transmitter 574, and receiver 572 describedabove. For example, in one embodiment, triangulation of cellular signalsmay be used to identify the approximate or exact geographical locationof the computing device system 500. In other embodiments, thepositioning system device 575 includes a proximity sensor ortransmitter, such as an RFID tag, that can sense or be sensed by devicesknown to be located proximate a merchant or other location to determinethat the computing device system 500 is located proximate these knowndevices. The positioning system device 575 may play a crucial role intransmitting location information associated with the computing devicesystem 500 for determining when the computing device system 500 is in,at, or is in close proximity to a particular geographic region.

The computing device system 500 further includes a power source 515,such as a battery, for powering various circuits and other devices thatare used to operate the computing device system 500. Embodiments of thecomputing device system 500 may also include a clock or other timer 550configured to determine and, in some cases, communicate actual orrelative time to the processor 510 or one or more other devices.

The computing device system 500 also includes a memory 520 operativelycoupled to the processor 510. As used herein, memory includes anycomputer-readable medium (as defined herein below) configured to storedata, code, or other information. The memory 520 may include volatilememory, such as volatile Random Access Memory (RAM) including a cachearea for the temporary storage of data. The memory 520 may also includenon-volatile memory, which can be embedded and/or may be removable. Thenon-volatile memory can additionally or alternatively include anelectrically erasable programmable read-only memory (EEPROM), flashmemory or the like.

The memory 520 can store any of a number of applications which includecomputer-executable instructions/code executed by the processor 510 toimplement the functions of the computing device system 500 and/or one ormore of the process/method steps described herein. For example, thememory 520 may include such applications as a web browser application522 and/or a notification application 521 (or any other applicationprovided by the managing entity system 200). These applications alsotypically instructions to a graphical user interface (GUI) on thedisplay 534 that allows the user 110 to interact with the computingdevice system 500, the managing entity system 200, and/or other devicesor systems. In one embodiment of the invention, when the user 110decides to enroll in a notification application 521 program, the user110 downloads, is assigned, or otherwise obtains the notificationapplication 521 from the managing entity system 200, or from a distinctapplication server (e.g., from the expected event identification system300). In other embodiments of the invention, the user 110 interacts withthe managing entity system 200 or the computing device system 500 viathe web browser application 522 in addition to, or instead of, thenotification application 521.

The memory 520 of the computing device system 500 may include a ShortMessage Service (SMS) application 523 configured to send, receive, andstore data, information, communications, alerts, and/or the like via thewireless telephone network 152.

The notification application 521 of the computing device system 500 maybe configured to receive alerts, triggering actions, and/or the likefrom the managing entity system 200 and/or the expected eventidentification system 300 that are in turn configured to cause the userinterface 530 to provide a message, notification, alert, and/or the liketo a customer (e.g., the user 110). The notification application 521 mayalso be configured to prompt the customer (e.g., the user 110) for userinput via the user input devices 540, to receive user input from theuser input devices 540, and the like.

The memory 520 can also store any of a number of pieces of information,and data, used by the computing device system 500 and the applicationsand devices that make up the computing device system 500 or are incommunication with the computing device system 500 to implement thefunctions of the computing device system 500 and/or the other systemsdescribed herein.

Referring now to FIG. 6 , a flowchart is provided to illustrate oneembodiment of a process 600 for triggering cross channel data caching onnetwork nodes, in accordance with embodiments of the invention. In someembodiments, the process 600 may include block 602, where the systemmonitors historical event data of a customer and live event data of thecustomer. The monitored customer data, in general, may includeinformation that is specific to particular users or customers, and mayinclude information or data that is specific to particular customertypes including, but not limited to, geographic region of the customer,account types of the customer, length of time a customer has had with arelationship with the managing entity, usage patterns of the customer,and/or the like.

The historical event data of a customer may be any data, information,data trends, or the like that can be used by the system to identify ordetermine correlations between certain triggering actions, theoccurrence of previous events, the timing of the occurrence of theprevious events, the channel(s) utilized by the user for each of theprevious events, and the like. For example, the historical event data ofthe customer may include information about triggering events that haveprompted the customer to interact with a managing entity associated withthis process 600. A triggering action may be the action of anotification being sent to the customer, where the notificationindicates that a payment cannot be processed, that an issue with anaccount of the user has been identified, and the like. The triggeringaction may also be an action performed by the user without a prompt bythe managing entity (e.g., purchasing a travel ticket to anothergeographic region, changing ownership or access rights to an accountassociated with the user, purchasing a particular product or service, orthe like). The historical event data may include information about whichevents appear to have been triggered by the triggering action. Forexample, if the triggering action was a notification that a transactioncannot be processed, the triggered event (i.e., historical event) mayhave been for the customer to call a customer support line of themanaging entity, call a representative of the customer that works forthe managing entity, log into an online portal, physically visit anoffice of the managing entity, interact with an automated teller machineassociated with the managing entity, interact with an electronic kioskof the managing entity, and/or the like.

The historical event data of the customer may further includeinformation about an amount of time between the triggering action andthe historical event (i.e., the time period between when the triggeringaction and a starting time of the historical event). For example, for aparticular historical event, the system may determine that the customercalled into a customer support line of the managing entity ten minutesafter receiving a notification that a transaction of the customer couldnot be processed. Furthermore, the system can determine how long eachhistorical event took, and store this information as historical eventdata.

The system can also store information about trends, averages, and otherstatistical information regarding the historical event data. Forexample, the system can determine that it takes the customer an averageof thirty minutes to call into a particular customer support line aftera particular triggering action, with a lower limit of ten minutes and anupper limit of two hours. The system can also determine an amount oftime that the customer was engaged in each historical event, an averageamount of time that the customer has been engaged in the same type ofhistorical events, lower and upper limits of the amount of time that thecustomer has been engaged in the same type of historical events, and thelike. As such, the system can store information about expected periodsof time that the customer may be engaging with that particular type ofevent. For example, the system can establish an expected period of timeof a particular type of event as beginning at the lower limit of theamount of time to begin the event, and lasting for the amount of timeassociated with the upper limit of how long the customer has beenengaged with the event. Of course, the system can also add or subtract acertain percentage (e.g. five percent, ten percent, or the like) orperiod of time (e.g., ten minutes, five hours, or the like) to theexpected period of time that the customer could be engaged with theparticular type of event. As noted above, the system may also take intoaccount or use the expected periods of time of other customers.

The historical event data may also identify one or more channels thatthe customer uses when interacting with the managing entity during eachhistorical event. As used herein, a “channel” is a mode of interactingwith the managing entity. The channels may include, but are not limitedto, dialing into a customer support line, dialing into a customerrepresentative line, dialing into an interactive voice response line,logging into or otherwise accessing an online portal, logging into orotherwise accessing a mobile application portal while in a particulargeographical region, and/or the like. As there are several potentialevents that may be likely or predictable for each triggering action, thesystem may identify a likelihood that the customer will interact witheach channel in response to a particular triggering event or triggeringevent type (each interaction, or the set of possible interactionstogether, being referred to as an expected event).

The monitored customer live event database may include data,information, alerts, news stories, current transaction data, and thelike that is associated with the particular customer, associated withthe particular type of customer, and/or associated with information thatmay have an impact on whether a triggering event is occurring or islikely to occur. The customer live event database data may includesimilar information to the customer historical event database, but thelive event database may receive constant, real-time, and/or nearreal-time updates to its data to inform the system oncurrently-occurring actions, notifications, incidents, and otheroccurrences that may trigger the subsequent occurrence of an expectedevent.

In some embodiments, the process 600 includes block 604, where thesystem determines an expected event based on the historical event dataof the customer and the live event data of the customer, where theexpected event includes one or more expected channels. The system mayanalyze, or have already analyzed, the historical customer eventdatabase to identify any trends in the customer's historical data and/orhistorical data of similar customers (e.g., customers with the same orsimilar characteristics) to identify matches between triggering actionsand expected events. In this way, the system may analyze the customerlive event database to determine that a triggering action is occurring,has occurred, or is likely to occur shortly. The system can thenidentify which expected event is associated with the identifiedtriggering action (e.g., from the customer historical event database oranother database where the linkages between known triggering actions andknown expected events are stored).

The system can also identify a triggering event from the customer liveevent database and then analyze the customer historical event databaseto determine an expected event based on the historical data of thecustomer, similar customers, and the identified triggering event.

The determination of the expected event may further include adetermination of an expected event period of time. As noted above, theexpected event period of time may include a beginning time (or date andtime), and an end date or time (e.g., start time plus maximum expectedduration of the expected event). In general, the expected event periodof time includes a period of time where it is anticipated that thecustomer is likely to interact with the managing entity through one ormore of the channels. For example, after the customer receives anotification of a transaction that the managing entity cannot process,the system may be able to expect that the user will dial in to acustomer support line between five minutes and three hours after thenotification, and that the interaction with the customer through thecustomer support line likely will last a maximum amount of thirtyminutes. The system can then set the expected event period of time tostart at five minutes after the notification and to end or conclude atthree hours and thirty minutes after the notification. In this way, thesystem can expect that one or more nodes of a network and/or one or morevirtual data structures on the nodes and/or the network associated withthe customer support line to need to have this customer's informationready for the duration of the expected time period, while these nodesand/or virtual data structures associated with the customer support linedo not regularly need to maintain this customer's data.

In some embodiments, the system may determine an expected event periodof time based on a configuration of the network. For example, the systemmay determine an expected event period of time based on a storage and/ornetwork structure of the one or more nodes and/or the network, such thatthe expected event period of time accounts for network latency, networkspeeds, proximity of one or more nodes to the expected channels, and/orthe like.

As the expected event may be associated with multiple channels, theexpected event period of time may be different for each channel.Therefore, the step of determining the expected event may furtherinclude determining an expected event period of time for each of the oneor more expected channels. For example, the system may have determinedthat the customer may additionally or alternatively interact with themanaging entity by physically visiting an office of the managing entity.The system may determine from the customer's historical event data thatthe customer's expected time period for this channel begins one hourafter the notification and ends after forty-eight hours.

While the expected time period for the one or more expected channels isdescribed as being determined based on the customer historical eventdatabase, the customer live event database, and/or the a configurationof the network, it should be known that the system may have preset orotherwise predetermined expected time periods that are based on thechannel, the customer, the geographic region, and/or the like. Forexample, these predetermined expected time periods may be determined bya specialist employee of the managing entity to cover the time periodduring which it is expected that one or more databases associated withthe expected channel(s) will need to locally store certain data relatedto the customer.

Additionally, in some embodiments, the process 600 includes block 606,where the system identifies, from the one or more systems of record, aset of data associated with the customer, based on the expected event.The system may, in some embodiments, identify all data that is relatedto the customer (e.g., account data of the customer, historicaltransaction data of the customer, pending transaction data of thecustomer, and/or the like).

Additionally, or alternatively, the system may identify certain datathat the customer likely will need access to, and/or that arepresentative or specialist employed by the managing entity will needaccess to, as part of the expected event. For example, if the triggeringaction includes a notification that a transaction for the customer couldnot be processed by the managing entity, the system may identify alldata from the systems of record that are related to the transaction, themerchant, the customer, the financial account being used by thecustomer, the financial instrument used by the customer, and/or thelike. In this way, the system may identify a subset of all customer datathat is likely needed for reference or information purposes by thecustomer and/or the managing entity during the expected event. By onlyidentifying the subset of customer data that is actually useful to thecustomer during the expected event, the system can reduce the computingresources required to transmit this data at a later point in time.

The step of identifying the set of data associated with the customerfrom the system(s) of record may further include a step of performing adata verification, validation, testing, and/or the like. If the systemdetermines that the identified data is incomplete or does not meet whatthe system expects will be needed to provide appropriate support to thecustomer during the expected event, the system can transmit anotification and information request to the customer and/or to aspecialist associated with the missing data, and receive the necessarydata at a point in time prior to, and/or during, the expected event.

In a similar manner, the system may check inputs associated with theexpected event to determine whether enough information has been acquiredand/or determined for the system to determine which customer data isneeded, what the expected period of time is, and/or at which channel(s)the customer data is needed. If the system determines that additionalinformation is needed for defining the expected event, the system cantransmit a notification and request for information from a specialistemployee of the managing entity system that is trained to identify theappropriate information and generate a corrected expected event that canbe used for the customer.

The process 600 may also include block 608, where the system caches theset of data associated with the customer to generate a set of cacheddata. Any caching application, module, computer processing unit cache,graphics processing unit cache, digital signal processors cache, diskcache, web cache, memorization cache, and/or the like that is configuredto reduce the size of a set of data. The set of data associated with thecustomer may be cached and stored in a particular format that may or maynot be compatible with possible channels.

In some embodiments, the process 600 includes block 610, where thesystem identifies one or more nodes of a network associated with each ofthe one or more expected channels, and where each of the one or morenodes is associated with one or more adapters configured to format theset of cached data into formats compatible with each of the one or moreexpected channels. For example, one or more nodes of the network may beassociated with or linked with one or more expected channels. In someembodiments, one or more nodes may be associated with or linked with oneor more expected channels by being physically proximate the one or moreexpected channels, proximate the one or more expected channels from anetwork architecture perspective, proximate the one or more expectedchannels within the network, and/or the like.

As noted, each of the one or more nodes may be associated with one ormore adapters configured to format the set of cached data into formatscompatible with each of the one or more expected channels. Each adaptermay be configured to convert the cached data into a format that isreadable or otherwise accessible to a particular channel. For example, afirst adapter may be configured to convert cached data into a formatthat is compatible with databases that are local to a channel of arecords system for a physical office. Additionally, a second adapter maybe configured to convert cached data into a format that is compatiblewith a database in a foreign geographical region that supports an onlineportal in that foreign geographical region. Furthermore, a third adaptermay be configured to convert cached data into a format that iscompatible with databases that are local to or otherwise linked with aninteractive voice response application channel. Additionally, oralternatively, when a channel extracts cached data from one or morenodes, one or more of the adapters may be configured to format thecached data into formats compatible with the channel extracting thecached data.

The process 600 may also include block 612, where the system generates,on each of the one or more nodes, a virtual data structure. For example,the system may transmit a command to one or more nodes to generate avirtual data structure for storage of the set of cached data, and theone or more nodes, based on the command, may generate the virtual datastructure. Additionally, or alternatively, the one or more nodes mayautomatically generate a virtual data structure for storage of the setof cached data based on receiving a command, receiving the set of cacheddata, and/or the like.

The process 600 may also include block 614, where the system transmitsthe set of cached data to the virtual data structure on each of the oneor more nodes, where the set of cached data is converted into theformats compatible with each of the one or more expected channels by theone or more adapters. For example, the system may include a transmitterserver, and the system may transmit, using the transmitter server, theset of cached data to one or more virtual data structures on one or morenodes of a network, where the one or more nodes are associated with theone or more expected channels. Additionally, or alternatively, one ormore adapters may be associated with the one or more nodes. In someembodiments, based on one or more of the one or more expected channelsextracting the set of cached data from the virtual data structuresand/or the nodes, the adapters may be configured to covert the set ofcached data into a format that is compatible with the one or moreexpected channels extracting the set of cached data. Additionally, oralternatively, the transmission of the cached data may be conductedthrough data sharding, data replication, and/or the like. In this way,the channels will be prepared for an interaction with the customer byhaving the customer's data readily available on the network. By storingthe cached data on nodes associated with or linked with one or moreexpected channels, the network may provide the customer's data with lowlatency, such that the data is readily available for extraction from thenetwork and use. This technique reduces the amount of time that it takesfor the customer data to be pulled up for displaying to the customerand/or a representative assisting the customer. Additionally, thetransmission of the cached data can be conducted at a point in time whenthe computing resources of the system are not strained by a large amountof data transmissions. Furthermore, by storing the cached data on nodesof the network, the system conserves computing resources that wouldotherwise be consumed by transmitting, receiving, storing, and furthertransmitting the cached data on local databases and/or serversassociated with the expected channels. For example, an amount ofcomputing resources (e.g., computers, servers, routers, and/or the like)owned, maintained, and/or the like by an entity for each of the expectedchannels may be reduced by storing the cached data on nodes of thenetwork.

In embodiments where the system has identified multiple expected periodsof time for the different channels, the system may order the channels towhich cached data is transmitted based on a starting date and time ofeach expected period of time. For example, the expected event may beassociated with a first channel of a call center with a first expectedperiod of time that starts ten minutes after the triggering eventoccurs, and the expected event may be associated with a second channelof a local office of the managing entity with a second expected periodof time that starts one hour after the triggering event occurs. In thisscenario, the system may prioritize the first channel (due to theearlier start time) and transmit the cached data to the nodes and/orvirtual data structures associated with the first channel before turningits computing resources to the task of transmitting the cached data tothe nodes and/or virtual data structures associated with the secondchannel.

In embodiments where the system has identified an expected event periodof time, the system may be configured to maintain the cached data ineach virtual data structure associated with each of the one or moreexpected channels for the expected event period of time. For example,the system may determine that the expected event period of time hasconcluded. Next, the system may determine that the expected event is notcurrently occurring (e.g., the user is not interacting with the managingentity via a mobile application, at an office of the managing entity, ona phone call with representatives of the managing entity, and/or thelike). In response to determining that the expected event period of timehas concluded, and in response to determining that the expected event isnot occurring, the system can automatically delete the cached data fromeach node and/or each virtual data structure associated with each of theone or more expected channels. In this way, the system can keep theamount of data stored at each node and/or virtual data structure linkedwith each channel at a lower amount than if the system was simplystoring customer data for any possible future interaction with themanaging entity through that channel. Furthermore, by reducing theamount of data stored in a node and/or virtual data structure, thesystem aides the effectiveness of the node and/or virtual data structureperformance.

If the expected event period of time is determined to have concluded,but the system determines that the expected event is occurring (e.g.,the user is interacting with the managing entity via a mobileapplication, at an office of the managing entity, on a phone call withrepresentatives of the managing entity, and/or the like), then thesystem can continue to maintain the cached data in each node and/orvirtual data structure of the one or more expected channels for at leastas long as the expected event is occurring. In this way, the systemensures that the customer data remains readily available to the customerand/or a specialist or representative that is assisting the customer forthe duration of the interaction, even if the interaction has gone beyondan expected time period.

The system may further be configured to maintain or delete the cacheddata that is stored in the nodes and/or virtual data structuresassociated with each of the one or more expected channels, based atleast in part on a determination that the customer has interacted with adifferent channel of the one or more expected channels. For example, thesystem may determine that the expected event includes either dialing into an interactive voice response system or (i.e., not “and” or “and/or”)accessing an online portal of the managing entity. If the system thendetermines that the customer has dialed in to the interactive voiceresponse system, then the system can automatically delete the cachedcustomer data from the node and/or virtual data structure linked withthe online portal because there is a very low chance that the customerwill also be accessing the online portal. Therefore, in someembodiments, the system may determine that the customer is interactingwith the managing entity through a first channel of the one or moreexpected channels, and automatically delete the cached data in all otherchannels of the one or more expected channels.

As an example of this process 600, the system may determine that theexpected event includes an expectation that the customer will access anonline portal while in a foreign geographic region. In such embodiments,the system may identify a first channel of the one or more expectedchannels as including an online portal linked to a first node of thenetwork located in the foreign geographic region. Therefore, whentransmitting the set of cached data to each node and/or virtual datastructure associated with each of the one or more expected channels, thesystem may transmit the set of cached data to the first node and/or afirst virtual data structure on the first node.

In another example of this process 600, the system may determine thatthe expected event includes an expectation that the customer willcontact a managing entity by calling the managing entity or byphysically visiting an office of the managing entity. In suchembodiments, the system may identify a first channel of the one or moreexpected channels that includes an interactive voice responseapplication (i.e., an application that is used when the customer callsthe managing entity) linked to a first node of the network.Additionally, the system may identify a second channel of the one ormore expected channels that includes an office records system associatedwith the office of the managing entity, where this office records systemis linked to a second node of the network. Therefore, transmitting theset of cached data each virtual data structure on each of the one ormore nodes includes transmitting the set of cached data to the firstvirtual data structure on the first node and to a second virtual datastructure on the second node.

In another example of this process 600, each node of the network may beconnected to another node of the network. Additionally, oralternatively, connected nodes of the network may include virtual datastructures including corresponding sets of cached data.

As will be appreciated by one of skill in the art, the present inventionmay be embodied as a method (including, for example, acomputer-implemented process, a business process, and/or any otherprocess), apparatus (including, for example, a system, machine, device,computer program product, and/or the like), or a combination of theforegoing. Accordingly, embodiments of the present invention may takethe form of an entirely hardware embodiment, an entirely softwareembodiment (including firmware, resident software, micro-code, and thelike), or an embodiment combining software and hardware aspects that maygenerally be referred to herein as a “system.” Furthermore, embodimentsof the present invention may take the form of a computer program producton a computer-readable medium having computer-executable program codeembodied in the medium.

Any suitable transitory or non-transitory computer-readable medium maybe utilized. The computer-readable medium may be, for example but notlimited to, an electronic, magnetic, optical, electromagnetic, infrared,or semiconductor system, apparatus, or device. More specific examples ofthe computer-readable medium include, but are not limited to, thefollowing: an electrical connection having one or more wires; a tangiblestorage medium such as a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), a compact discread-only memory (CD-ROM), or other optical or magnetic storage device.

In the context of this document, a computer-readable medium may be anymedium that can contain, store, communicate, or transport the programfor use by or in connection with the instruction execution system,apparatus, or device. The computer usable program code may betransmitted using any appropriate medium, including but not limited tothe Internet, wireline, optical fiber cable, radio frequency (RF)signals, or other mediums.

Computer-executable program code for carrying out operations ofembodiments of the present invention may be written in an objectoriented, scripted or unscripted programming language such as Java,Perl, Smalltalk, C++, or the like. However, the computer program codefor carrying out operations of embodiments of the present invention mayalso be written in procedural programming languages, such as the “C”programming language or similar programming languages.

Embodiments of the present invention are described above with referenceto flowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products. It will be understood thateach block of the flowchart illustrations and/or block diagrams, and/orcombinations of blocks in the flowchart illustrations and/or blockdiagrams, can be implemented by computer-executable program codeportions. These computer-executable program code portions may beprovided to a processor of a general purpose computer, special purposecomputer, or other programmable data processing apparatus to produce aparticular machine, such that the code portions, which execute via theprocessor of the computer or other programmable data processingapparatus, create mechanisms for implementing the functions/actsspecified in the flowchart and/or block diagram block or blocks.

These computer-executable program code portions may also be stored in acomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the code portions stored in the computer-readablememory produce an article of manufacture including instructionmechanisms which implement the function/act specified in the flowchartand/or block diagram block(s).

The computer-executable program code may also be loaded onto a computeror other programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer-implemented process such that the codeportions which execute on the computer or other programmable apparatusprovide steps for implementing the functions/acts specified in theflowchart and/or block diagram block(s). Alternatively, computer programimplemented steps or acts may be combined with operator or humanimplemented steps or acts in order to carry out an embodiment of theinvention.

As the phrase is used herein, a processor may be “configured to” performa certain function in a variety of ways, including, for example, byhaving one or more general-purpose circuits perform the function byexecuting particular computer-executable program code embodied incomputer-readable medium, and/or by having one or moreapplication-specific circuits perform the function.

Embodiments of the present invention are described above with referenceto flowcharts and/or block diagrams. It will be understood that steps ofthe processes described herein may be performed in orders different thanthose illustrated in the flowcharts. In other words, the processesrepresented by the blocks of a flowchart may, in some embodiments, be inperformed in an order other that the order illustrated, may be combinedor divided, or may be performed simultaneously. It will also beunderstood that the blocks of the block diagrams illustrated, in someembodiments, merely conceptual delineations between systems and one ormore of the systems illustrated by a block in the block diagrams may becombined or share hardware and/or software with another one or more ofthe systems illustrated by a block in the block diagrams. Likewise, adevice, system, apparatus, and/or the like may be made up of one or moredevices, systems, apparatuses, and/or the like. For example, where aprocessor is illustrated or described herein, the processor may be madeup of a plurality of microprocessors or other processing devices whichmay or may not be coupled to one another. Likewise, where a memory isillustrated or described herein, the memory may be made up of aplurality of memory devices which may or may not be coupled to oneanother.

While certain exemplary embodiments have been described and shown in theaccompanying drawings, it is to be understood that such embodiments aremerely illustrative of, and not restrictive on, the broad invention, andthat this invention not be limited to the specific constructions andarrangements shown and described, since various other changes,combinations, omissions, modifications and substitutions, in addition tothose set forth in the above paragraphs, are possible. Those skilled inthe art will appreciate that various adaptations and modifications ofthe just described embodiments can be configured without departing fromthe scope and spirit of the invention. Therefore, it is to be understoodthat, within the scope of the appended claims, the invention may bepracticed other than as specifically described herein.

The invention claimed is:
 1. A system for triggering cross channel datacaching on network nodes, the system comprising: a memory device; and aprocessing device operatively coupled to the memory device, wherein theprocessing device is configured to execute computer-readable programcode to: monitor historical event data of a customer and live event dataof the customer; determine an expected event based on the historicalevent data of the customer and the live event data of the customer,wherein the expected event comprises one or more expected channels froma plurality of channels; determine an expected event period of theexpected event based on a configuration of a network, wherein thenetwork comprises a plurality of nodes, wherein each channel of theplurality of channels is linked with at least one node of the pluralityof nodes, and wherein the expected event period is determined based onstorage and a structure of the network to account for latency of thenetwork, speed of the network, and proximity of one or more nodes to theone or more expected channels; identify, from one or more systems ofrecord, a set of data associated with the customer, based on theexpected event; cache the set of data associated with the customer togenerate a set of cached data; identify the one or more nodes of anetwork proximate each of the one or more expected channels, whereineach of the one or more nodes is associated with one or more adaptersconfigured to format the set of cached data into formats compatible witheach of the one or more expected channels; generate, on each of the oneor more nodes, a virtual data structure; and transmit the set of cacheddata to the virtual data structure on each of the one or more nodes forstorage on the network in each virtual data structure on each of the oneor more nodes for the expected event period, wherein the one or moreadapters convert the set of cached data from the virtual data structureon each of the one or more nodes into the formats compatible with eachof the one or more expected channels when the one or more expectedchannels extract the set of cached data from the virtual data structureon each of the one or more nodes on the network.
 2. The system of claim1, wherein the processing device is further configured to executecomputer-readable program code to: determine that the expected eventperiod of time has concluded; determine that the expected event is notoccurring; and in response to determining that the expected event periodof time has concluded, and in response to determining that the expectedevent is not occurring, delete the set of cached data from each virtualdata structure on each of the one or more nodes.
 3. The system of claim1, wherein the processing device is further configured to executecomputer-readable program code to: determine that the expected event isoccurring; determine that the expected event period of time hasconcluded; and maintain the set of cached data in each virtual datastructure on each of the one or more nodes for at least as long as theexpected event is occurring.
 4. The system of claim 1, whereindetermining the expected event further comprises determining an expectedevent period of time for each of the one or more expected channels. 5.The system of claim 1, wherein the expected event comprises anexpectation that the customer will access an online portal while in aforeign geographic region, wherein a first channel of the one or moreexpected channels comprises the online portal linked to a first node ofthe network located in the foreign geographic region, and whereintransmitting the set of cached data to each virtual data structure oneach of the one or more nodes comprises transmitting the set of cacheddata to the first node.
 6. The system of claim 1, wherein the expectedevent comprises an expectation that the customer will contact a managingentity by calling the managing entity or by physically visiting anoffice of the managing entity, wherein a first channel of the one ormore expected channels comprises an interactive voice responseapplication linked to a first node of the network, wherein a secondchannel of the one or more expected channels comprises an office recordssystem associated with the office of the managing entity that is linkedto a second node of the network, and wherein transmitting the set ofcached data to each virtual data structure on each of the one or morenodes comprises transmitting the set of cached data to a first virtualdata structure on the first node and to a second virtual data structureon the second node.
 7. The system of claim 1, wherein each node of thenetwork is connected to another node of the network, and whereinconnected nodes of the network comprise virtual data structurescomprising corresponding sets of cached data.
 8. A computer programproduct for triggering cross channel data caching on network nodes, thecomputer program product comprising at least one non-transitorycomputer-readable medium comprising computer-readable instructions, theinstructions comprising instructions for: monitoring historical eventdata of a customer and live event data of the customer; determining anexpected event based on the historical event data of the customer andthe live event data of the customer, wherein the expected eventcomprises one or more expected channels from a plurality of channels;determining an expected event period of the expected event based on aconfiguration of a network, wherein the network comprises a plurality ofnodes, wherein each channel of the plurality of channels is linked withat least one node of the plurality of nodes, and wherein the expectedevent period is determined based on storage and a structure of thenetwork to account for latency of the network, speed of the network, andproximity of one or more nodes to the one or more expected channels;identifying, from one or more systems of record, a set of dataassociated with the customer, based on the expected event; caching theset of data associated with the customer to generate a set of cacheddata; identifying the one or more nodes of a network proximate each ofthe one or more expected channels, wherein each of the one or more nodesis associated with one or more adapters configured to format the set ofcached data into formats compatible with each of the one or moreexpected channels; generating on each of the one or more nodes a virtualdata structure; and transmitting the set of cached data to the virtualdata structure on each of the one or more nodes for storage on thenetwork in each virtual data structure on each of the one or more nodesfor the expected event period, wherein the one or more adapters convertthe set of cached data from the virtual data structure on each of theone or more nodes into the formats compatible with each of the one ormore expected channels when the one or more expected channels extractthe set of cached data from the virtual data structure on each of theone or more nodes on the network.
 9. The computer program product ofclaim 8, wherein the computer-readable instructions further compriseinstructions for: determining that the expected event period of time hasconcluded; determining that the expected event is not occurring; and inresponse to determining that the expected event period of time hasconcluded, and in response to determining that the expected event is notoccurring, deleting the set of cached data from each virtual datastructure on each of the one or more nodes.
 10. The computer programproduct of claim 8, wherein the computer-readable instructions furthercomprise instructions for: determining that the expected event isoccurring; determining that the expected event period of time hasconcluded; and maintaining the set of cached data in each virtual datastructure on each of the one or more nodes for at least as long as theexpected event is occurring.
 11. The computer program product of claim8, wherein determining the expected event further comprises determiningan expected event period of time for each of the one or more expectedchannels.
 12. The computer program product of claim 8, wherein theexpected event comprises an expectation that the customer will access anonline portal while in a foreign geographic region, wherein a firstchannel of the one or more expected channels comprises the online portallinked to a first node of the network located in the foreign geographicregion, and wherein transmitting the set of cached data to each virtualdata structure on each of the one or more nodes comprises transmittingthe set of cached data to the first node.
 13. The computer programproduct of claim 8, wherein the expected event comprises an expectationthat the customer will contact a managing entity by calling the managingentity or by physically visiting an office of the managing entity,wherein a first channel of the one or more expected channels comprisesan interactive voice response application linked to a first node of thenetwork, wherein a second channel of the one or more expected channelscomprises an office records system associated with the office of themanaging entity that is linked to a second node of the network, andwherein transmitting the set of cached data to each database associatedwith each of the one or more expected channels comprises transmittingthe set of cached data to a first virtual data structure on the firstnode and to a second virtual data structure on the second node.
 14. Thecomputer program product of claim 8, wherein each node of the network isconnected to another node of the network, and wherein connected nodes ofthe network comprise virtual data structures comprising correspondingsets of cached data.
 15. A computer implemented method for triggeringcross channel data caching on network nodes, the computer implementedmethod comprising: providing a computing system comprising a computerprocessing device and a non-transitory computer-readable medium, wherethe computer-readable medium comprises configured computer programinstruction code, such that when the instruction code is operated by thecomputer processing device, the computer processing device performs thefollowing operations: monitoring historical event data of a customer andlive event data of the customer; determining an expected event based onthe historical event data of the customer and the live event data of thecustomer, wherein the expected event comprises one or more expectedchannels from a plurality of channels; determining an expected eventperiod of the expected event based on a configuration of a network,wherein the network comprises a plurality of nodes, wherein each channelof the plurality of channels is linked with at least one node of theplurality of nodes, and wherein the expected event period is determinedbased on storage and a structure of the network to account for latencyof the network, speed of the network, and proximity of one or more nodesto the one or more expected channels; identifying, from one or moresystems of record, a set of data associated with the customer, based onthe expected event; caching the set of data associated with the customerto generate a set of cached data; identifying the one or more nodes of anetwork proximate each of the one or more expected channels, whereineach of the one or more nodes is associated with one or more adaptersconfigured to format the set of cached data into formats compatible witheach of the one or more expected channels; generating on each of the oneor more nodes a virtual data structure; and transmitting the set ofcached data to the virtual data structure on each of the one or morenodes for storage on the network in each virtual data structure on eachof the one or more nodes for the expected event period, wherein the oneor more adapters convert the set of cached data from the virtual datastructure on each of the one or more nodes into the formats compatiblewith each of the one or more expected channels when the one or moreexpected channels extract the set of cached data from the virtual datastructure on each of the one or more nodes on the network.
 16. Thecomputer implemented method of claim 15, wherein the computer programinstruction code comprises computer program instruction code, such thatwhen the instruction code is operated by the computer processing device,the computer processing device performs the following operations:determining that the expected event period of time has concluded;determining that the expected event is not occurring; and in response todetermining that the expected event period of time has concluded, and inresponse to determining that the expected event is not occurring,deleting the set of cached data from each virtual data structure on eachof the one or more nodes.
 17. The computer implemented method of claim15, wherein the computer program instruction code comprises computerprogram instruction code, such that when the instruction code isoperated by the computer processing device, the computer processingdevice performs the following operations: determining that the expectedevent is occurring; determining that the expected event period of timehas concluded; and maintaining the set of cached data in each virtualdata structure on each of the one or more nodes for at least as long asthe expected event is occurring.
 18. The computer implemented method ofclaim 15, wherein determining the expected event further comprisesdetermining an expected event period of time for each of the one or moreexpected channels.
 19. The computer implemented method of claim 15,wherein the expected event comprises an expectation that the customerwill access an online portal while in a foreign geographic region,wherein a first channel of the one or more expected channels comprisesthe online portal linked to a first node of the network located in theforeign geographic region, and wherein transmitting the set of cacheddata to each virtual data structure on each of the one or more nodescomprises transmitting the set of cached data to the first node.
 20. Thecomputer implemented method of claim 15, wherein the expected eventcomprises an expectation that the customer will contact a managingentity by calling the managing entity or by physically visiting anoffice of the managing entity, wherein a first channel of the one ormore expected channels comprises an interactive voice responseapplication linked to a first node of the network, wherein a secondchannel of the one or more expected channels comprises an office recordssystem associated with the office of the managing entity that is linkedto a second node of the network, and wherein transmitting the set ofcached data to each database associated with each of the one or moreexpected channels comprises transmitting the set of cached data to afirst virtual data structure on the first node and to a second virtualdata structure on the second node.